Lcs data compression/decompression system

ABSTRACT

An LCS data compression/decompression system includes an orchestrator device in a resource system with a host operating system and coupled to a storage system via a network. The orchestrator device receives a read instruction from the host operating system directed to data stored in the storage system and, in response, retrieves and uses a data read decompression policy to select one of the storage system and the orchestrator device to perform data decompression operations on the data. The orchestrator device then provides a data read decompression instruction to the storage system to cause the storage system to provide the data to the orchestrator device such that the orchestrator device provides the data to the host operation system after the one of the storage system and the orchestrator device selected using the data read decompression policy performs the data decompression operations on the data.

BACKGROUND

The present disclosure relates generally to information handlingsystems, and more particularly to compressing and decompressing data forLogically Composed Systems (LCSs) that are provided using informationhandling systems.

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

While conventional information handling systems such as, for example,server devices and/or other computing devices known in the art havetraditionally been provided with particular information handling systemscomponents that configure it to satisfy one or more use cases, newcomputing paradigms provide for the allocation of resources frominformation handling systems and/or information handling systemcomponents for use in Logically Composed Systems (LCSs) that may becomposed as needed to satisfy any computing intent/workload, and thendecomposed such that those resources may be utilized in other LCSs. Assuch, users of the LCSs may be provided with LCSs that meet theircurrent needs for any particular workload they require.

For example, LCSs are often provided using Bare Metal Server (BMS)systems or other resource systems known in the art, with resourcedevices included within and/or outside of those resource systems (e.g.,processing devices and memory devices on a motherboard in the BMS systemused to provide an Operating System (OS) for the LCS, storage devices,networking devices, etc.) used to perform the functionality for theLCSs, and often dynamically changing over the time period in which theLCS is provided. Furthermore, orchestrator devices in the BMS systemsmay orchestrate the provisioning of those LCSs while also includingresource devices that may be utilized to provide the functionality ofthose LCSs. As such, LCSs are disaggregated systems and their associatedfunctionality may be enabled from a variety of different sources andlocations (e.g., from resource devices within the BMS system discussedabove, resource devices included on the orchestrator device in the BMSsystem discussed above, resource devices outside the BMS systemdiscussed above, etc.), and the inventors of the present disclosure haverecognized that such multi-source/multi-location functionalityavailability presents opportunities for efficiency improvements.

For example, conventional systems like the server devices discussedabove sometimes operate to store data in network-attached storagesystems, with the server devices transmitting data to thenetwork-attached storage system as part of a write operation, and thenetwork-attached storage system operating to compress that data toproduce compressed data, and then store that compressed data to completethe write operation. Subsequently, the server device may request thedata from the network-attached storage system as part of a readoperation, and the network-attached storage subsystem will operate toretrieve the compressed data from storage, decompress that data, andthen provide that decompressed data to the server device to complete theread operation. However, the inventors of the present disclosure haverecognized that the compression/decompression functionality discussedabove will be available from multiple sources and locations in thedisaggregated systems/LCSs discussed above, and thus conventionalperformance of the compression and decompression functionality duringthe write operations and/or read operations in the manner discussedabove will suffer from inefficiencies in many scenarios if duplicatedfor LCSs.

Accordingly, it would be desirable to provide an LCS datacompression/decompression system that addresses the issues discussedabove.

SUMMARY

According to one embodiment, an Information Handling System (IHS)includes a processing system; and a memory system that is coupled to theprocessing system and that includes instructions that, when executed bythe processing system, cause the processing system to provide aLogically Composed System (LCS) orchestrator engine that is configuredto: receive, from a host operating system, a read instruction to performa read operation on data that is stored in a storage system; retrieve,in response to receiving the read instruction, a data read decompressionpolicy; select, using the data read decompression policy, one of thestorage system and the LCS orchestrator engine to perform datadecompression operations on the data; and provide, to the storage systemvia a network, a data read decompression instruction that is configuredto cause the storage system to provide the data to the LCS orchestratorengine such that the LCS orchestrator engine provides the data to thehost operation system after the one of the storage system and the LCSorchestrator device selected using the data read decompression policyperforms the data decompression operations on the data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view illustrating an embodiment of an InformationHandling System (IHS).

FIG. 2 is a schematic view illustrating an embodiment of an LCSprovisioning system.

FIG. 3 is a schematic view illustrating an embodiment of an LCSprovisioning subsystem that may be included in the LCS provisioningsystem of FIG. 2 .

FIG. 4 is a schematic view illustrating an embodiment of a resourcesystem that may be included in the LCS provisioning subsystem of FIG. 3.

FIG. 5 is a schematic view illustrating an embodiment of theprovisioning of an LCS using the LCS provisioning system of FIG. 2 .

FIG. 6 is a schematic view illustrating an embodiment of theprovisioning of an LCS using the LCS provisioning system of FIG. 2 .

FIG. 7A is a schematic view illustrating an embodiment of an LCS datacompression/decompression system provided according to the teachings ofthe present disclosure.

FIG. 7B is a schematic view illustrating an embodiment of the LCS datacompression/decompression system provided of FIG. 7A.

FIG. 8 is a flow chart illustrating an embodiment of a method forcompressing data for an LCS.

FIG. 9A is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 8 .

FIG. 9B is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 8 .

FIG. 9C is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 8 .

FIG. 9D is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 8 .

FIG. 10 is a flow chart illustrating an embodiment of a method fordecompressing data for an LCS.

FIG. 11A is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 10 .

FIG. 11B is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 10 .

FIG. 11C is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 10 .

FIG. 11D is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 10 .

FIG. 11E is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 10 .

FIG. 11F is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 10 .

FIG. 11G is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 10 .

FIG. 11H is a schematic view illustrating an embodiment of the LCS datacompression/decompression system of FIG. 7A operating during the methodof FIG. 10 .

DETAILED DESCRIPTION

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, calculate, determine, classify, process, transmit, receive,retrieve, originate, switch, store, display, communicate, manifest,detect, record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer (e.g., desktop or laptop), tablet computer, mobile device(e.g., personal digital assistant (PDA) or smart phone), server (e.g.,blade server or rack server), a network storage device, or any othersuitable device and may vary in size, shape, performance, functionality,and price. The information handling system may include random accessmemory (RAM), one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic, ROM, and/orother types of nonvolatile memory. Additional components of theinformation handling system may include one or more disk drives, one ormore network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse,touchscreen and/or a video display. The information handling system mayalso include one or more buses operable to transmit communicationsbetween the various hardware components.

In one embodiment, IHS 100, FIG. 1 , includes a processor 102, which isconnected to a bus 104. Bus 104 serves as a connection between processor102 and other components of IHS 100. An input device 106 is coupled toprocessor 102 to provide input to processor 102. Examples of inputdevices may include keyboards, touchscreens, pointing devices such asmouses, trackballs, and trackpads, and/or a variety of other inputdevices known in the art. Programs and data are stored on a mass storagedevice 108, which is coupled to processor 102. Examples of mass storagedevices may include hard discs, optical disks, magneto-optical discs,solid-state storage devices, and/or a variety of other mass storagedevices known in the art. IHS 100 further includes a display 110, whichis coupled to processor 102 by a video controller 112. A system memory114 is coupled to processor 102 to provide the processor with faststorage to facilitate execution of computer programs by processor 102.Examples of system memory may include random access memory (RAM) devicessuch as dynamic RAM (DRAM), synchronous DRAM (SDRAM), solid state memorydevices, and/or a variety of other memory devices known in the art. Inan embodiment, a chassis 116 houses some or all of the components of IHS100. It should be understood that other buses and intermediate circuitscan be deployed between the components described above and processor 102to facilitate interconnection between the components and the processor102.

As discussed in further detail below, the Logically Composed System(LCS) data compression/decompression systems and methods of the presentdisclosure may be utilized with Logically Composed Systems (LCSs), whichone of skill in the art in possession of the present disclosure willrecognize may be provided to users as part of an intent-based,as-a-Service delivery platform that enables multi-cloud computing whilekeeping the corresponding infrastructure that is utilized to do so“invisible” to the user in order to, for example, simplify theuser/workload performance experience. As such, the LCSs discussed hereinenable relatively rapid utilization of technology from a relativelybroader resource pool, optimize the allocation of resources to workloadsto provide improved scalability and efficiency, enable seamlessintroduction of new technologies and value-add services, and/or providea variety of other benefits that would be apparent to one of skill inthe art in possession of the present disclosure.

With reference to FIG. 2 , an embodiment of a LCS provisioning system200 is illustrated that may be utilized with the LCS datacompression/decompression systems and methods of the present disclosure.In the illustrated embodiment, the LCS provisioning system 200 includesone or more client devices 202. In an embodiment, any or all of theclient devices may be provided by the IHS 100 discussed above withreference to FIG. 1 and/or may include some or all of the components ofthe IHS 100, and in specific examples may be provided by desktopcomputing devices, laptop/notebook computing devices, tablet computingdevices, mobile phones, and/or any other computing device known in theart. However, while illustrated and discussed as being provided byspecific computing devices, one of skill in the art in possession of thepresent disclosure will recognize that the functionality of the clientdevice(s) 202 discussed below may be provided by other computing devicesthat are configured to operate similarly as the client device(s) 202discussed below, and that one of skill in the art in possession of thepresent disclosure would recognize as utilizing the LCSs describedherein. As illustrated, the client device(s) 202 may be coupled to anetwork 204 that may be provided by a Local Area Network (LAN), theInternet, combinations thereof, and/or any of network that would beapparent to one of skill in the art in possession of the presentdisclosure.

As also illustrated in FIG. 2 , a plurality of LCS provisioningsubsystems 206 a, 206 b, and up to 206 c are coupled to the network 204such that any or all of those LCS provisioning subsystems 206 a-206 cmay provide LCSs to the client device(s) 202 as discussed in furtherdetail below. In an embodiment, any or all of the LCS provisioningsubsystems 206 a-206 c may include one or more of the IHS 100 discussedabove with reference to FIG. 1 and/or may include some or all of thecomponents of the IHS 100. For example, in some of the specific examplesprovided below, each of the LCS provisioning subsystems 206 a-206 c maybe provided by a respective datacenter or other computingdevice/computing component location (e.g., a respective one of the“clouds” that enables the “multi-cloud” computing discussed above) inwhich the components of that LCS provisioning subsystem are included.However, while a specific configuration of the LCS provisioning system200 (e.g., including multiple LCS provisioning subsystems 206 a-206 c)is illustrated and described, one of skill in the art in possession ofthe present disclosure will recognize that other configurations of theLCS provisioning system 200 (e.g., a single LCS provisioning subsystem,LCS provisioning subsystems that span multiple datacenters/computingdevice/computing component locations, etc.) will fall within the scopeof the present disclosure as well.

With reference to FIG. 3 , an embodiment of an LCS provisioningsubsystem 300 is illustrated that may provide any of the LCSprovisioning subsystems 206 a-206 c discussed above with reference toFIG. 2 . As such, the LCS provisioning subsystem 300 may include one ormore of the IHS 100 discussed above with reference to FIG. 1 and/or mayinclude some or all of the components of the IHS 100, and in thespecific examples provided below may be provided by a datacenter orother computing device/computing component location in which thecomponents of the LCS provisioning subsystem 300 are included. However,while a specific configuration of the LCS provisioning subsystem 300 isillustrated and described, one of skill in the art in possession of thepresent disclosure will recognize that other configurations of the LCSprovisioning subsystem 300 will fall within the scope of the presentdisclosure as well.

In the illustrated embodiment, the LCS provisioning subsystem 300 isprovided in a datacenter 302, and includes a resource management system304 coupled to a plurality of resource systems 306 a, 306 b, and up to306 c. In an embodiment, any of the resource management system 304 andthe resource systems 306 a-306 c may be provided by the IHS 100discussed above with reference to FIG. 1 and/or may include some or allof the components of the IHS 100. In the specific embodiments providedbelow, each of the resource management system 304 and the resourcesystems 306 a-306 c may include an orchestrator device. In someembodiments, the orchestrator device may be provided by the SystemControl Processor (SCP) device or Data Processing Unit (DPU) devicediscussed below, and may be conceptualized as an “enhanced” SmartNICdevice that may be configured to perform functionality that is notavailable in conventional SmartNIC devices such as, for example, theresource management functionality, LCS provisioning functionality,and/or other SCP/DPU functionality described herein. However, whiledescribed as being provided by an SCP device or DPU device, one of skillin the art in possession of the present disclosure will appreciate howthe orchestrator device of the present disclosure may also be providedby other devices that have been configured to perform the orchestratorfunctionality described below while remaining within the scope of thepresent disclosure as well.

In an embodiment, any of the resource systems 306 a-306 c may includeany of the resources described below coupled to an SCP device or DPUdevice that is configured to facilitate management of those resources bythe resource management system 304. Furthermore, the SCP device or DPUdevice included in the resource management system 304 may provide an SCPManager (SCPM) subsystem or DPU Manager (DPUM) subsystem that isconfigured to manage the SCP devices or DPU devices in the resourcesystems 306 a-306 c, and that performs the functionality of the resourcemanagement system 304 described below. In some examples, the resourcemanagement system 304 may be provided by a “stand-alone” system (e.g.,that is provided in a separate chassis from each of the resource systems306 a-306 c), and the SCPM subsystem or DPUM subsystem discussed belowmay be provided by a dedicated SCP device, DPU device, processing/memoryresources, and/or other components in that resource management system304. However, in other embodiments, the resource management system 304may be provided by one of the resource systems 306 a-306 c (e.g., it maybe provided in a chassis of one of the resource systems 306 a-306 c),and the SCPM subsystem or DPUM subsystem may be provided by an SCPdevice, DPU device, processing/memory resources, and/or any other anyother components in that resource system.

As such, the resource management system 304 is illustrated with dashedlines in FIG. 3 to indicate that it may be a stand-alone system in someembodiments, or may be provided by one of the resource systems 306 a-306c in other embodiments. Furthermore, one of skill in the art inpossession of the present disclosure will appreciate how SCP devices orDPU devices in the resource systems 306 a-306 c may operate to “elect”or otherwise select one or more of those SCP devices or DPU devices tooperate as the SCPM subsystem or DPUM subsystem that provides theresource management system 304 described below. However, while aspecific configuration of the LCS provisioning subsystem 300 isillustrated and described, one of skill in the art in possession of thepresent disclosure will recognize that other configurations of the LCSprovisioning subsystem 300 will fall within the scope of the presentdisclosure as well.

With reference to FIG. 4 , an embodiment of a resource system 400 isillustrated that may provide any or all of the resource systems 306a-306 c discussed above with reference to FIG. 3 . In an embodiment, theresource system 400 may be provided by the IHS 100 discussed above withreference to FIG. 1 and/or may include some or all of the components ofthe IHS 100. In the illustrated embodiment, the resource system 400includes a chassis 402 that houses the components of the resource system400, only some of which are illustrated and discussed below. In theillustrated embodiment, the chassis 402 houses an SCP device 406, butone of skill in the art in possession of the present disclosure willappreciate how the SCP device 406 may be replaced by the DPU devicedescribed herein while remaining within the scope of the presentdisclosure, with that DPU device provided by BLUEFIELD® DPU devicesavailable from NVIDIA® Corporation of Santa Clara, California, UnitedStates, DPU devices available from FUNGIBLE® Inc. of Santa Clara,California, United States, and/or other DPU devices known in the art.

In an embodiment, the SCP device 406 may include a processing system(not illustrated, but which may include the processor 102 discussedabove with reference to FIG. 1 ) and a memory system (not illustrated,but which may include the memory 114 discussed above with reference toFIG. 1 ) that is coupled to the processing system and that includesinstructions that, when executed by the processing system, cause theprocessing system to provide an SCP engine that is configured to performthe functionality of the SCP engines and/or SCP devices discussed below.Furthermore, the SCP device 406 may also include any of a variety of SCPcomponents (e.g., hardware/software) that are configured to enable anyof the SCP functionality described below.

In the illustrated embodiment, the chassis 402 also houses a pluralityof resource devices 404 a, 404 b, and up to 404 c, each of which iscoupled to the SCP device 406. For example, the resource devices 404a-404 c may include processing systems (e.g., first type processingsystems such as those available from INTEL® Corporation of Santa Clara,California, United States, second type processing systems such as thoseavailable from ADVANCED MICRO DEVICES (AMD)® Inc. of Santa Clara,California, United States, Advanced Reduced Instruction Set Computer(RISC) Machine (ARM) devices, Graphics Processing Unit (GPU) devices,Tensor Processing Unit (TPU) devices, Field Programmable Gate Array(FPGA) devices, accelerator devices, etc.); memory systems (e.g.,Persistence MEMory (PMEM) devices (e.g., solid state byte-addressablememory devices that reside on a memory bus), etc.); storage devices(e.g., Non-Volatile Memory express over Fabric (NVMe-oF) storagedevices, Just a Bunch Of Flash (JBOF) devices, etc.); networking devices(e.g., Network Interface Controller (NIC) devices, etc.); and/or anyother devices that one of skill in the art in possession of the presentdisclosure would recognize as enabling the functionality described asbeing enabled by the resource devices 404 a-404 c discussed below. Assuch, the resource devices 404 a-404 c in the resource systems 306 a-306c/400 may be considered a “pool” of resources that are available to theresource management system 304 for use in composing LCSs.

To provide a specific example, the SCP devices described herein mayprovide a “trusted” orchestrator device that operates as a Root-of-Trust(RoT) for their corresponding resource devices/systems, to provide anintent management engine for managing the workload intents discussedbelow, to perform telemetry generation and/or reporting operations fortheir corresponding resource devices/systems, to perform identityoperations for their corresponding resource devices/systems, provide animage boot engine (e.g., an operating system image boot engine) for LCSscomposed using a processing system/memory system controlled by that SCPdevice, and/or perform any other operations that one of skill in the artin possession of the present disclosure would recognize as providing thefunctionality described below. For example, the SCP device 406 may be“trusted” because it provides a root-of-trust for its correspondingresource devices/systems, and thus may be configured with restrictedaccess to its hardware and/or software that has been validated and ismaintained within a closed-loop infrastructure. For example, the SCPdevice 704 may run cryptographically signed software validated via theroot-of-trust, with connectivity to both a BMS BMC and the SCPM devicediscussed above, and with all communications internal to the closed-loopinfrastructure secured to ensure their veracity.

To contrast, the DPU device described herein may provide an “untrusted”orchestrator device that may include similarhardware/software/capabilities as the SCP device 406, but a user of theSCP device 406 may not be able to access suchhardware/software/capabilities on the SCP device 406 unless it is partof/connected to an authorized network. As will be appreciated by one ofskill in the art in possession of the present disclosure, the DPU devicemay be “untrusted” due to it having not been manufactured by amanufacturer of the computing system 202 (e.g., it may be obtained bythe manufacturer of the computing system 202 from any of a variety ofvendors that are not controlled by the manufacturer of the computingsystem 202), it having not been secured based on a lack of control overthe DPU device 204 by a manufacturer of the computing system 202, and/orbased on other “untrusted” factors that would be apparent to one ofskill in the art in possession of the present disclosure. As will beappreciated by one of skill in the art in possession of the presentdisclosure, a DPU device software stack differs from a conventionalInput/Output (TO) card that uses firmware configured to providededicated I/O and management functions, as in addition to firmware, theDPU device software stack will include a DPU operating system and a userspace that is customizable to configure/program the DPU device topresent resource devices to an operating system in the computing system202 outside the control of the manufacturer of the computing system,which can render that DPU device “untrusted” in many scenarios.

As discussed below, the SCP devices and/or DPU devices described hereinmay include Software-Defined Storage (SDS) subsystems, inferencesubsystems, data protection subsystems, Software-Defined Networking(SDN) subsystems, trust subsystems, data management subsystems,compression subsystems, encryption subsystems, and/or any otherhardware/software described herein that may be allocated to an LCS thatis composed using the resource devices/systems controlled by that SCPdevice. However, while an SCP device is illustrated and described asperforming the functionality discussed below, one of skill in the art inpossession of the present disclosure will appreciated that functionalitydescribed herein may be enabled on the DPU devices discussed above, aswell as other devices with similar functionality, while remaining withinthe scope of the present disclosure as well.

Thus, the resource system 400 may include the chassis 402 including theSCP device 406 connected to any combinations of resource devices. Toprovide a specific embodiment, the resource system 400 may provide a“Bare Metal Server” that one of skill in the art in possession of thepresent disclosure will recognize may be a physical server system thatprovides dedicated server hosting to a single tenant, and thus mayinclude the chassis 402 housing a processing system and a memory system,the SCP device 406, as well as any other resource devices that would beapparent to one of skill in the art in possession of the presentdisclosure. However, in other specific embodiments, the resource system400 may include the chassis 402 housing the SCP device 406 coupled toparticular resource devices 404 a-404 c. For example, the chassis 402 ofthe resource system 400 may house a plurality of processing systems(i.e., the resource devices 404 a-404 c) coupled to the SCP device 406.In another example, the chassis 402 of the resource system 400 may housea plurality of memory systems (i.e., the resource devices 404 a-404 c)coupled to the SCP device 406. In another example, the chassis 402 ofthe resource system 400 may house a plurality of storage devices (i.e.,the resource devices 404 a-404 c) coupled to the SCP device 406. Inanother example, the chassis 402 of the resource system 400 may house aplurality of networking devices (i.e., the resource devices 404 a-404 c)coupled to the SCP device 406. However, one of skill in the art inpossession of the present disclosure will appreciate that the chassis402 of the resource system 400 housing a combination of any of theresource devices discussed above will fall within the scope of thepresent disclosure as well.

As discussed in further detail below, the SCP device 406 in the resourcesystem 400 will operate with the resource management system 304 (e.g.,an SCPM subsystem) to allocate any of its resources devices 404 a-404 cfor use in a providing an LCS. Furthermore, the SCP device 406 in theresource system 400 may also operate to allocate SCP hardware and/orperform functionality, which may not be available in a resource devicethat it has allocated for use in providing an LCS, in order to provideany of a variety of functionality for the LCS. For example, the SCPengine and/or other hardware/software in the SCP device 406 may beconfigured to perform encryption functionality, compressionfunctionality, and/or other storage functionality known in the art, andthus if that SCP device 406 allocates storage device(s) (which may beincluded in the resource devices it controls) for use in a providing anLCS, that SCP device 406 may also utilize its own SCP hardware and/orsoftware to perform that encryption functionality, compressionfunctionality, and/or other storage functionality as needed for the LCSas well. However, while particular SCP-enabled storage functionality isdescribed herein, one of skill in the art in possession of the presentdisclosure will appreciate how the SCP devices 406 described herein mayallocate SCP hardware and/or perform other enhanced functionality for anLCS provided via allocation of its resource devices 404 a-404 c whileremaining within the scope of the present disclosure as well.

With reference to FIG. 5 , an example of the provisioning of an LCS 500to one of the client device(s) 202 is illustrated. For example, the LCSprovisioning system 200 may allow a user of the client device 202 toexpress a “workload intent” that describes the general requirements of aworkload that the user would like to perform (e.g., “I need an LCS with10 gigahertz (GHz) of processing power and 8 gigabytes (GB) of memorycapacity for an application requiring 20 terabytes (TB) ofhigh-performance protected-object-storage for use with ahospital-compliant network”, or “I need an LCS for a machine-learningenvironment requiring Tensorflow processing with 3 TB s of AcceleratorPMEM memory capacity”). As will be appreciated by one of skill in theart in possession of the present disclosure, the workload intentdiscussed above may be provided to one of the LCS provisioningsubsystems 206 a-206 c, and may be satisfied using resource systems thatare included within that LCS provisioning subsystem, or satisfied usingresource systems that are included across the different LCS provisioningsubsystems 206 a-206 c.

As such, the resource management system 304 in the LCS provisioningsubsystem that received the workload intent may operate to compose theLCS 500 using resource devices 404 a-404 c in the resource systems 306a-306 c/400 in that LCS provisioning subsystem, and/or resource devices404 a-404 c in the resource systems 306 a-306 c/400 in any of the otherLCS provisioning subsystems. FIG. 5 illustrates the LCS 500 including aprocessing resource 502 allocated from one or more processing systemsprovided by one or more of the resource devices 404 a-404 c in one ormore of the resource systems 306 a-306 c/400 in one or more of the LCSprovisioning subsystems 206 a-206 c, a memory resource 504 allocatedfrom one or more memory systems provided by one or more of the resourcedevices 404 a-404 c in one or more of the resource systems 306 a-306c/400 in one or more of the LCS provisioning subsystems 206 a-206 c, anetworking resource 506 allocated from one or more networking devicesprovided by one or more of the resource devices 404 a-404 c in one ormore of the resource systems 306 a-306 c/400 in one or more of the LCSprovisioning subsystems 206 a-206 c, and/or a storage resource 508allocated from one or more storage devices provided by one or more ofthe resource devices 404 a-404 c in one or more of the resource systems306 a-306 c/400 in one or more of the LCS provisioning subsystems 206a-206 c.

Furthermore, as will be appreciated by one of skill in the art inpossession of the present disclosure, any of the processing resource502, memory resource 504, networking resource 506, and the storageresource 508 may be provided from a portion of a processing system(e.g., a core in a processor, a time-slice of processing cycles of aprocessor, etc.), a portion of a memory system (e.g., a subset of memorycapacity in a memory device), a portion of a storage device (e.g., asubset of storage capacity in a storage device), and/or a portion of anetworking device (e.g., a portion of the bandwidth of a networkingdevice). Further still, as discussed above, the SCP device(s) 406 in theresource systems 306 a-306 c/400 that allocate any of the resourcedevices 404 a-404 c that provide the processing resource 502, memoryresource 504, networking resource 506, and the storage resource 508 inthe LCS 500 may also allocate their SCP hardware and/or perform enhancedfunctionality (e.g., the enhanced storage functionality in the specificexamples provided above) for any of those resources that may otherwisenot be available in the processing system, memory system, storagedevice, or networking device allocated to provide those resources in theLCS 500.

With the LCS 500 composed using the processing resources 502, the memoryresources 504, the networking resources 506, and the storage resources508, the resource management system 304 may provide the client device202 resource communication information such as, for example, InternetProtocol (IP) addresses of each of the systems/devices that provide theresources that make up the LCS 500, in order to allow the client device202 to communicate with those systems/devices in order to utilize theresources that make up the LCS 500. As will be appreciated by one ofskill in the art in possession of the present disclosure, the resourcecommunication information may include any information that allows theclient device 202 to present the LCS 500 to a user in a manner thatmakes the LCS 500 appear the same as an integrated physical systemhaving the same resources as the LCS 500.

Thus, continuing with the specific example above in which the userprovided the workload intent defining an LCS with a 10 GHz of processingpower and 8 GB of memory capacity for an application with 20 TB ofhigh-performance protected object storage for use with ahospital-compliant network, the processing resources 502 in the LCS 500may be configured to utilize 10 GHz of processing power from processingsystems provided by resource device(s) in the resource system(s), thememory resources 504 in the LCS 500 may be configured to utilize 8 GB ofmemory capacity from memory systems provided by resource device(s) inthe resource system(s), the storage resources 508 in the LCS 500 may beconfigured to utilize 20 TB of storage capacity from high-performanceprotected-object-storage storage device(s) provided by resourcedevice(s) in the resource system(s), and the networking resources 506 inthe LCS 500 may be configured to utilize hospital-compliant networkingdevice(s) provided by resource device(s) in the resource system(s).

Similarly, continuing with the specific example above in which the userprovided the workload intent defining an LCS for a machine-learningenvironment for Tensorflow processing with 3 TB s of Accelerator PMEMmemory capacity, the processing resources 502 in the LCS 500 may beconfigured to utilize TPU processing systems provided by resourcedevice(s) in the resource system(s), and the memory resources 504 in theLCS 500 may be configured to utilize 3 TB of accelerator PMEM memorycapacity from processing systems/memory systems provided by resourcedevice(s) in the resource system(s), while any networking/storagefunctionality may be provided for the networking resources 506 andstorage resources 508 if needed.

With reference to FIG. 6 , another example of the provisioning of an LCS600 to one of the client device(s) 202 is illustrated. As will beappreciated by one of skill in the art in possession of the presentdisclosure, many of the LCSs provided by the LCS provisioning system 200will utilize a “compute” resource (e.g., provided by a processingresource such as an x86 processor, an AMD processor, an ARM processor,and/or other processing systems known in the art, along with a memorysystem that includes instructions that, when executed by the processingsystem, cause the processing system to perform any of a variety ofcompute operations known in the art), and in many situations thosecompute resources may be allocated from a Bare Metal Server (BMS) andpresented to a client device 202 user along with storage resources,networking resources, other processing resources (e.g., GPU resources),and/or any other resources that would be apparent to one of skill in theart in possession of the present disclosure.

As such, in the illustrated embodiment, the resource systems 306 a-306 cavailable to the resource management system 304 include a Bare MetalServer (BMS) 602 having a Central Processing Unit (CPU) device 602 a anda memory system 602 b, a BMS 604 having a CPU device 604 a and a memorysystem 604 b, and up to a BMS 606 having a CPU device 606 a and a memorysystem 606 b. Furthermore, one or more of the resource systems 306 a-306c includes resource devices 404 a-404 c provided by a storage device610, a storage device 612, and up to a storage device 614. Furtherstill, one or more of the resource systems 306 a-306 c includes resourcedevices 404 a-404 c provided by a Graphics Processing Unit (GPU) device616, a GPU device 618, and up to a GPU device 620.

FIG. 6 illustrates how the resource management system 304 may composethe LCS 600 using the BMS 604 to provide the LCS 600 with CPU resources600 a that utilize the CPU device 604 a in the BMS 604, and memoryresources 600 b that utilize the memory system 604 b in the BMS 604.Furthermore, the resource management system 304 may compose the LCS 600using the storage device 614 to provide the LCS 600 with storageresources 600 d, and using the GPU device 318 to provide the LCS 600with GPU resources 600 c. As illustrated in the specific example in FIG.6 , the CPU device 604 a and the memory system 604 b in the BMS 604 maybe configured to provide an operating system 600 e that is presented tothe client device 202 as being provided by the CPU resources 600 a andthe memory resources 600 b in the LCS 600, with operating system 600 eutilizing the GPU device 618 to provide the GPU resources 600 c in theLCS 600, and utilizing the storage device 614 to provide the storageresources 600 d in the LCS 600. The user of the client device 202 maythen provide any application(s) on the operating system 600 e providedby the CPU resources 600 a/CPU device 604 a and the memory resources 600b/memory system 604 b in the LCS 600/BMS 604, with the application(s)operating using the CPU resources 600 a/CPU device 604 a, the memoryresources 600 b/memory system 604 b, the GPU resources 600 c/GPU device618, and the storage resources 600 d/storage device 614.

Furthermore, as discussed above, the SCP device(s) 406 in the resourcesystems 306 a-306 c/400 that allocates any of the CPU device 604 a andmemory system 604 b in the BMS 604 that provide the CPU resource 600 aand memory resource 600 b, the GPU device 618 that provides the GPUresource 600 c, and the storage device 614 that provides storageresource 600 d, may also allocate SCP hardware and/or perform enhancedfunctionality (e.g., the enhanced storage functionality in the specificexamples provided above) for any of those resources that may otherwisenot be available in the CPU device 604 a, memory system 604 b, storagedevice 614, or GPU device 618 allocated to provide those resources inthe LCS 500.

However, while simplified examples are described above, one of skill inthe art in possession of the present disclosure will appreciate howmultiple devices/systems (e.g., multiple CPUs, memory systems, storagedevices, and/or GPU devices) may be utilized to provide an LCS.Furthermore, any of the resources utilized to provide an LCS (e.g., theCPU resources, memory resources, storage resources, and/or GPU resourcesdiscussed above) need not be restricted to the same device/system, andinstead may be provided by different devices/systems over time (e.g.,the GPU resources 600 c may be provided by the GPU device 618 during afirst time period, by the GPU device 616 during a second time period,and so on) while remaining within the scope of the present disclosure aswell. Further still, while the discussions above imply the allocation ofphysical hardware to provide LCSs, one of skill in the art in possessionof the present disclosure will recognize that the LCSs described hereinmay be composed similarly as discussed herein from virtual resources.For example, the resource management system 304 may be configured toallocate a portion of a logical volume provided in a Redundant Array ofIndependent Disk (RAID) system to an LCS, allocate a portion/time-sliceof GPU processing performed by a GPU device to an LCS, and/or performany other virtual resource allocation that would be apparent to one ofskill in the art in possession of the present disclosure in order tocompose an LCS.

Similarly as discussed above, with the LCS 600 composed using the CPUresources 600 a, the memory resources 600 b, the GPU resources 600 c,and the storage resources 600 d, the resource management system 304 mayprovide the client device 202 resource communication information suchas, for example, Internet Protocol (IP) addresses of each of thesystems/devices that provide the resources that make up the LCS 600, inorder to allow the client device 202 to communicate with thosesystems/devices in order to utilize the resources that make up the LCS600. As will be appreciated by one of skill in the art in possession ofthe present disclosure, the resource communication information allowsthe client device 202 to present the LCS 600 to a user in a manner thatmakes the LCS 600 appear the same as an integrated physical systemhaving the same resources as the LCS 600.

As will be appreciated by one of skill in the art in possession of thepresent disclosure, the LCS provisioning system 200 discussed abovesolves issues present in conventional Information Technology (IT)infrastructure systems that utilize “purpose-built” devices (serverdevices, storage devices, etc.) in the performance of workloads and thatoften result in resources in those devices being underutilized. This isaccomplished, at least in part, by having the resource managementsystem(s) 304 “build” LCSs that satisfy the needs of workloads when theyare deployed. As such, a user of a workload need simply define the needsof that workload via a “manifest” expressing the workload intent of theworkload, and resource management system 304 may then compose an LCS byallocating resources that define that LCS and that satisfy therequirements expressed in its workload intent, and present that LCS tothe user such that the user interacts with those resources in samemanner as they would physical system at their location having those sameresources.

Referring now to FIG. 7A, an embodiment of an LCS datacompression/decompression system 700 provided according to the teachingsof the present disclosure is illustrated. The LCS datacompression/decompression system 700 includes a resource system that, inthe illustrated embodiment, is provided by a BMS system 702 that may beprovided by any of the resource systems 304 a-304 c and 400 and/or theBMS systems 602-604 discussed above. In the illustrated embodiment, theBMS system 702 includes a chassis 704 that houses the components of theBMS system 702, only some of which are illustrated and discussed below.For example, the chassis 704 may house a BMS processing system 706(e.g., the processor 102 discussed above with reference to FIG. 1 , aCentral Processing Unit (CPU), etc.) and a memory system (notillustrated, but which may include the memory 114 discussed above withreference to FIG. 1 ) that is coupled to the BMS processing system 706and that includes instructions that, when executed by the BMS processingsystem 706, cause the BMS processing system 706 to provide a hostoperating system 708 for an LCS that is configured to perform thefunctionality of the host operating systems discussed below.

The chassis 704 may also house an orchestrator device 710 that may beprovided by the SCP devices, DPU devices, and/or other orchestratordevices discussed above. In the illustrated embodiment, the orchestratordevice 710 may include an orchestrator processing system (notillustrated, but which may include the processor 102 discussed abovewith reference to FIG. 1 ) and an orchestrator memory system (notillustrated, but which may include the memory 114 discussed above withreference to FIG. 1 ) that is coupled to the orchestrator processingsystem and that includes instructions that, when executed by theorchestrator processing system, cause the orchestrator processing systemto provide an orchestrator engine 712 that is configured to perform thefunctionality of the orchestrator engines and/or orchestrator devicesdiscussed below.

The orchestrator device 710 may also include a storage system (notillustrated, but which may include the storage 108 discussed above withreference to FIG. 1 ) that is coupled to the orchestrator engine 712(e.g., via a coupling between the storage system and the orchestratorprocessing system) and that includes an orchestrator database 714 thatis configured to store any of the information utilized by theorchestrator engine 712 discussed below. The orchestrator device 710 mayalso house a communication system 716 that is coupled to theorchestrator engine 712 (e.g., via a coupling between the communicationsystem 716 and the orchestrator processing system) and that may beprovided by a Network Interface Controller (NIC), wireless communicationsystems (e.g., BLUETOOTH®, Near Field Communication (NFC) components,WiFi components, etc.), and/or any other communication components thatwould be apparent to one of skill in the art in possession of thepresent disclosure.

In the illustrated embodiment, the communication system 716 in theorchestrator device 710 is coupled to a network 718 that may be providedby a Local Area Network (LAN), the Internet, combinations thereof,and/or other networks that would be apparent to one of skill in the artin possession of the present disclosure. Furthermore, a plurality ofstorage systems 720 a, 720 b, and up to 720 c are coupled to the network718 in a manner that allows the orchestrator device 710 to store andretrieve data from those storage systems 720 a-720 c via the network718. In an embodiment, any or all of the storage systems 720 a-720 c maybe provided by the IHS 100 discussed above with reference to FIG. 1 ,and/or may include some or all of the components of the IHS 100, andspecific examples may be provided by server device(s) with storageresources. However, while described as server devices with storageresources, one of skill in the art in possession of the presentdisclosure will appreciate how the storage systems 720 a-720 c may beprovided by a variety of other storage systems and/or components whileremaining within the scope of the present disclosure as well. Asdiscussed below, in some embodiments one or more of the storage systems720 a-720 c may be configured to perform data compression and/ordecompression functionality, while in other embodiments, one or more ofthe storage systems 720 a-720 c may not be configured to perform datacompression and/or decompression functionality. Furthermore, while thestorage systems 720 a-720 c are illustrated as network-connected storagesystems (i.e., from the point of view of the orchestrator device 710),other embodiments may include at least one of the storage systems 720a-720 c included in the chassis 704 of the BMS system 702.

As discussed above, the components illustrated in FIG. 7A may beutilized to provide an LCS for a client device. For example, the BMSprocessing system 706 may operate as discussed above to provide the hostoperating system 708 for an LCS that was composed by the resourcemanagement system 304 discussed above and provided with the assistanceof the orchestrator device 710. Furthermore, as also discussed above,resource devices included within and/or outside the chassis 704 of theBMS system 702 may be utilized by the orchestrator device 710 to providethe LCS, with the storage systems 720 a-720 c providing just a fewexamples of network-connected resource devices that are being utilizedto provide the LCS. As such, while a client device and LCS are notexplicitly illustrated in the examples provided below, one of skill inthe art in possession of the present disclosure will appreciate how thedata write operations and data read operations may be performed at theinstruction of the host operating system 708 during the operation of anLCS that utilizes the host operating system 708, the orchestrator device710, and the storage systems 720 a-720 c.

As discussed below, the orchestrator device 710 may be configured toperform data compression and/or decompression functionality. Forexample, with reference to FIG. 7B, the orchestrator engine 712discussed above with reference to FIG. 7A may provide an orchestratoroperating system 722 for the orchestrator device 710. In the illustratedembodiment, the orchestrator operating system 722 provides an emulatedstorage device 722 a that is described as being provided by an emulatedNon-Volatile Memory express (NVMe) storage device in the specificexamples provided below, although one of skill in the art in possessionof the present disclosure will appreciate how other storage device typesmay be emulated by the orchestrator operating system 7212 whileremaining within the scope of the present disclosure as well. As such,the orchestrator operating system 722 may be configured to present theemulated storage device 722 a to one or more storage drivers 708 aprovided by the host operating system 708, which may allow container(s),application(s), and/or virtual machine(s) provided by the host operatingsystem 708 to utilize the emulated storage device 722 a via the storagedriver(s) 708 a as if it were one or more physical storage devices(i.e., the write and read data as described below).

As also illustrated in FIG. 7B, the orchestrator operating system 722may also provide a storage controller 722 b for the emulated storagedevice 722 a that may be configured to perform any of the storagecontrol operations discussed below for the emulated storage device 722a. Furthermore, the orchestrator operating system 722 may also provide ablock device 722 c that one of skill in the art in possession of thepresent disclosure will recognize is a storage abstraction that may bepresented as a storage disk to the storage systems 720 a-720 c whensending or receiving data as discussed below. The orchestrator operatingsystem 722 may also provide a compression service 722 d that one ofskill in the art in possession of the present disclosure will appreciatemay be enabled via compression/decompression hardware that is includedon the orchestrator device 710. Finally, the orchestrator operatingsystem 722 may also provide a storage client 722 e that one of skill inthe art in possession of the present disclosure will appreciate isconfigured to provide the communication with the storage systems 720a-720 c discussed below. However, while a specific LCS datacompression/decompression system 700 and orchestrator device 710 havebeen illustrated and described, one of skill in the art in possession ofthe present disclosure will recognize that the LCS datacompression/decompression systems and/or orchestrator devices of thepresent disclosure may include a variety of components and/or componentconfigurations for providing conventional functionality, as well as thefunctionality discussed below, while remaining within the scope of thepresent disclosure as well.

Referring now to FIG. 8 , an embodiment of a method 800 for compressingdata for a Logically Composed System (LCS) is illustrated. As discussedbelow, the systems and methods of the present disclosure provide fordynamic, policy-based utilization of compression functionality on an LCSorchestrator device and a storage system used with an LCS in order toperform efficient data compression operations, and may take into accountproperties of the data, the state of LCS resource devices, and/or otherfactors in order to perform the efficient data compression operationsdiscussed above while ensuring performance levels for the LCS/LCSresource devices. For example, the LCS data compression system of thepresent disclosure may include an orchestrator device in a resourcesystem with a host operating system and coupled to a storage system viaa network. The orchestrator device receives a write instruction from thehost operating system with data provided for storage in the storagesystem and, in response, retrieves and uses a data write compressionpolicy to select at least one of the storage systems and theorchestrator device to perform data compression operations on the data.The orchestrator device then provides a data write compressioninstruction to the storage system to cause the storage system to storethe data after the at least one of the storage systems and theorchestrator device selected using the data write compression policyperforms the data compression operations on the data. As such, theefficiency of data compression in a disaggregated system with a varietyof compression resources and locations is improved.

The method 800 begins at block 802 where an orchestrator device and astorage system(s) share compression capabilities. With reference to FIG.9A, in an embodiment of block 802, the storage systems 720 a-720 c andthe orchestrator engine 712 in the orchestrator device 710 may performcompression capability exchange operations 900 that may include theorchestrator engine 712 transmitting its compression capabilities viathe communication system 716 and through the network 718 to each of thestorage systems 720 a-720 c, and each of the storage systems 720 a-720 ctransmitting their respective compression capabilities through thenetwork 718 and to the orchestrator engine 712 via its communicationsystem 716. As illustrated in FIG. 9A, in response to receiving thecompression capabilities from the storage systems 720 a-720 c, theorchestrator engine 712 may perform compression capability storageoperations 902 that include storage those compression capabilities inthe orchestrator database 714.

In an embodiment, the compression capabilities transmitted during thecompression capability exchange operations 900 may include anidentification of whether compression functionality is available, a typeof compression capability that is available (e.g., a compressionalgorithm that will be used in compression operations), any of the datawrite compression polic(ies) discussed below, a protocol format forgenerating the compression metadata discussed below, and/or any othercompression capability information that one of skill in the art inpossession of the present disclosure would recognize as allowing for thefunctionality discussed below. In some embodiments of block 802, thecompression capability exchange operations 900 may include, or befollowed by, compression negotiation operations between the storagesystems 720 a-720 c and the orchestrator engine 712 in the orchestratordevice 710 in order to, for example, negotiate the use of compatiblecompression functionality by the orchestrator engine 712 and any of thestorage systems 720 a-720 c. However, while the exchange of compressioncapability information and the negotiation of compression functionalityhas been described, one of skill in the art in possession of the presentdisclosure will recognize that other information may be exchanged and/orother functionality negotiated in order to provide the functionalitydiscussed below while remaining within the scope of the presentdisclosure as well.

The method 800 then proceeds to block 804 where the orchestrator devicereceives a data write instruction including data for storage. Withreference to FIG. 9B, in an embodiment of block 804, the orchestratorengine 712 in the orchestrator device 710 may perform data writeinstruction receiving operations 904 that include receiving a data writeinstruction from the host operating system 708. For example, the hostoperating system 708 provided for the LCS discussed above may receive aninstruction from a user (e.g., via a container, application, and/orvirtual machine provided by the host operating system 708 as discussedabove) to store data and, in response, the host operating system 708 maygenerate and transmit a data write instruction that includes that datato the orchestrator engine 712 in the orchestrator device 710. As willbe appreciated by one of skill in the art in possession of the presentdisclosure, the data provided with the data write instruction at block804 may be uncompressed data, and may include any of a variety ofend-to-end data protection information that would be apparent to one ofskill in the art in possession of the present disclosure.

To provide a specific example in which the emulated storage device 722 ais an emulated NVMe storage device 722 a, at block 804 a host NVMeinitiator provided by the host operating system 708 may provide the datawrite instruction in an NVMe storage device submission queue of theemulated NVMe storage device 722 a, and then may ring a doorbell for theemulated NVMe storage device 722 a. In response, the emulated NVMestorage device 722 a/storage controller 722 b will read the NVMe storagedevice submission queue to retrieve the data write instruction. However,while a specific example is provided, one of skill in the art inpossession of the present disclosure will appreciate that theorchestrator engine 712 in the orchestrator device 710 may receive thedata write instruction in a variety of manners that will fall within thescope of the present disclosure as well.

The method 800 then proceeds to block 806 where the orchestrator deviceuses a data write compression policy to select the storage system and/orthe orchestrator device to perform data compression operations on thedata. With reference to FIG. 9C, in an embodiment of block 806, theorchestrator engine 712 in the orchestrator device 710 may perform datawrite compression policy retrieval operations 906 that include accessinga data write compression policy that is stored in the orchestratordatabase 714. As will be appreciated by one of skill in the art inpossession of the present disclosure, the data write compressionpolicies described herein may be provided in orchestrator devices inresource systems (e.g., in the orchestrator device 710 in the BMS system702 in FIG. 9C) by an administrator of the LCS provisioning systemdiscussed above, and may define how data compression should be performedfor any LCS provided using that orchestrator device and thedisaggregated resource devices discussed above. As such, the data writecompression policy retrieved at block 806 may have been generated andstored in the orchestrator database 714 prior to the method 800, andmany include any of a variety of policy details that provide for thedata compression functionality described below.

As will be appreciated by one of skill in the art in possession of thepresent disclosure, the data write compression policy may include any ofa variety of policy details that define when, where, and how data willbe compressed as part of a data write operation. For example, arelatively simple data write compression policy may define a data sizeunder which data will be transmitted for storage in a storage systemwithout performing data compression operations on that data, and overwhich data compression operations will be performed on that data priorto transmitting that data for storage in the storage system. As such,the data write compression policy may consider data transfer bandwidthsavings (e.g., data transfer bandwidth savings realized via thetransmission of compressed data vs. decompressed data) when determininghow, when, and where to perform data compression operations.

In another example, another relatively simple data write compressionpolicy may define an orchestrator device processing bandwidth underwhich data will be transmitted for storage in a storage system withoutperforming data compression operations on that data, and over which datacompression operations will be performed on that data prior totransmitting that data for storage in the storage system. In anotherexample, another relatively simple data write compression policy maydefine a storage system processing bandwidth over which data will betransmitted for storage in a storage system without performing datacompression operations on that data, and under which data compressionoperations will be performed on that data prior to transmitting thatdata for storage in the storage system. For example, the orchestratordevice may be configured to receive or retrieve storage systemprocessing system telemetry data or other information that is indicativeof the storage system processing bandwidth discussed above, and utilizethat with the data write compression policy discussed above. As such,the data write compression policy may consider CPU utilization (e.g.,current CPU utilization in either or both of the orchestrator device andthe storage system) when determining how, when, and where to performdata compression operations.

In another example, another relatively simple data write compressionpolicy may define a network bandwidth over which data will betransmitted for storage in a storage system without performing datacompression operations on that data, and under which data compressionoperations will be performed on that data prior to transmitting thatdata for storage in the storage system. For example, the orchestratordevice may be configured to identify a network bandwidth based on anamount of data traffic that is being transmitted via its communicationsystem 716 (e.g., via a NIC port that is coupled to the network 718). Assuch, the data write compression policy may consider data transferbandwidth (e.g., data transfer bandwidth currently available in thenetwork) when determining how, when, and where to perform datacompression operations.

Furthermore, one of skill in the art in possession of the presentdisclosure will appreciate how the relatively simple data writecompression policies discussed above may be combined to generaterelatively more complex data write compression policies that considerdata size, orchestrator processing bandwidth, storage system processingbandwidth, network bandwidth, as well as any other factors that would beapparent to one of skill in the art in possession of the presentdisclosure. For example, at block 806 the orchestrator engine 712 in theorchestrator device 710 may select the storage system 720 a and/or theorchestrator device 710 to perform data compression operations based ona data block/shard size, processing statistics generated by the storagesystem 720 a and/or orchestrator device 710, network statistics, otherinformation that may be indicative of a network bottleneck, etc.However, while a few specific data write compression policies have beendescribed, one of skill in the art in possession of the presentdisclosure will appreciate how a variety of data write compressionpolicies of varying complexity may define when, where, and howcompression should be performed prior to storing data in a storagesystem while remaining within the scope of the present disclosure aswell.

One of skill in the art in possession of the present disclosure willrecognize that the orchestrator engine 712 in the orchestrator device710 may have access to any of a variety of information about theoperation of the LCS (and the resource devices used to provide that LCS)in order to utilize the data write compression policy to select astorage system and/or the orchestrator device to perform datacompression operations on the data. For example, in order to determinethe orchestrator device processing bandwidth discussed above, theorchestrator engine 712 may have access to orchestrator processingsystem telemetry data and/or other operating information. Similarly, inorder to determine the storage system processing bandwidth discussedabove, the orchestrator engine 712 may have access to storage systemprocessing system telemetry data and/or other operating information viathe network 718. Similarly as well, in order to determine the networkbandwidth discussed above, the orchestrator engine 712 may have accessto network operating information via its communication system 716, withthe network operating information including directly measured operatinginformation (e.g., via its NIC port as described above) or indirectlymeasured operating information (e.g., provided via directly measuredoperation information that is indicative of the indirectly measuredoperating information).

As such, at block 806, the orchestrator engine 712 in the orchestratordevice 710 may use the data write compression policy and any of theinformation discussed above in order to select at least one of thestorage systems 720 a-720 c and the orchestrator device 710 to performdata compression operations on the data. In some of the specificexamples provided below, the orchestrator engine 712 in the orchestratordevice 710 selects the storage system 720 a for performing compressionoperations and/or storing the data, but one of skill in the art inpossession of the present disclosure will appreciate how the otherstorage systems 720 b-720 c may be selected to perform the compressionoperations and/or store the data while remaining within the scope of thepresent disclosure as well. For example, some embodiments of block 806may include the orchestrator engine 712 in the orchestrator device 710using the data write compression policy and any of the informationdiscussed above in order to select the orchestrator device 710 toperform data compression operations on the data. In another example,some embodiments of block 806 may include the orchestrator engine 712 inthe orchestrator device 710 using the data write compression policy andany of the information discussed above in order to select the storagesystem 720 a to perform data compression operations on the data. In yetanother example, some embodiments of block 806 may include theorchestrator engine 712 in the orchestrator device 710 using the datawrite compression policy and any of the information discussed above inorder to select both the storage system 720 a and the orchestratordevice 710 to perform data compression operations on the data.

In embodiments in which the orchestrator engine 712 in the orchestratordevice 710 selects the orchestrator device 710 to perform datacompression operations on the data, the orchestrator engine 712 mayoperate to compress the data received from the host operating system 708to provide compressed data. Continuing with the specific example inwhich the emulated storage device 722 a is an emulated NVMe storagedevice 722 a, at block 806 the NVMe storage device 722 a/storagecontroller 722 b may provide the data in the data write instruction tothe compression service 722 d in order to compress that data to providethe compressed data. Following the compression of the data to providethe compressed data, the orchestrator engine 712 in the orchestratordevice 710 may generate compression metadata that may include any of avariety of details about the compression of that data, and provide thecompressed data in a data write compression instruction. As discussed infurther detail below, the compression metadata may include any detailsabout the compression of data that would be required by another deviceor system that did not perform that compression in order to decompressthat data, and allows the decompression operations discussed below to beperformed by any decompression-enabled resource device that provides thedisaggregated system/LCS regardless of where the compression operationswere performed.

For example, the compression metadata generated as discussed above mayidentify a compression algorithm that was used to compress the data, acompression ratio of the decompressed data to the compressed data, asize of the decompressed data, a size of the compressed data, a checksumfor the compressed data, and/or any other compression metadata that oneof skill in the art in possession of the present disclosure wouldrecognize as providing for the decompression functionality describedbelow. Furthermore, one of skill in the art in possession of the presentdisclosure will appreciate how if the orchestrator engine 712 in theorchestrator device 710 selects both the storage system 720 a and theorchestrator device 710 to perform data compression operations on thedata, the orchestrator engine 712 may operate to compress the datareceived from the host operating system 708 in the data writeinstruction to provide compressed data, generate compression metadatathat includes the details of the compression of that data, and providethe compressed data in a data write compression instruction similarly asdiscussed above. In embodiments in which the orchestrator engine 712 inthe orchestrator device 710 selects the storage system 720 a to performdata compression operations on the data, the orchestrator engine 712 mayoperate to provide the uncompressed data in a data write compressioninstruction.

The method 800 then proceeds to block 808 where the orchestrator deviceprovides a data write compression instruction to the storage system tocause the storage system to store the data after the storage systemand/or the orchestrator device selected using the data write compressionpolicy perform data compression operations on the data. With referenceto FIG. 9D, in an embodiment of block 808, the orchestrator engine 712in the orchestrator device 710 may perform data write compressioninstruction transmission operations 908 that include transmitting thedata write compression instruction via its communication system 716 andthrough the network 718 to the storage system 720 a.

Continuing with the example above in which the orchestrator device 710performed data compression operations on the data received from the hostoperating system 708, the data write compression instruction may includethe compressed data, the compression metadata, and/or any otherinformation that would be apparent to one of skill in the art inpossession of the present disclosure as allowing for the functionalitydescribed below. In an embodiment, in response to receiving the datawrite compression instruction, the storage system 720 a may store thecompressed data and its compression metadata in one or more storagedevices included in the storage system 720 a.

Continuing with the example above in which the storage system 720 a wasselected to perform data compression operations on the data receivedfrom the host operating system 708, the data write compressioninstruction may include the uncompressed data and/or any otherinformation that would be apparent to one of skill in the art inpossession of the present disclosure as allowing for the functionalitydescribed below. In an embodiment, in response to receiving the datawrite compression instruction, the storage system 720 a may compress thedecompressed data to provide compressed data, generate compressionmetadata that includes the details of the compression of that datasubstantially similarly as discussed above, and store the compresseddata and its compression metadata in one or more storage devicesincluded in the storage system 720 a.

Continuing with the example above in which both the orchestrator device710 and the storage system 720 a were selected to perform datacompression operations on the data received from the host operatingsystem 708, the data write compression instruction may include thecompressed data (which was compressed by the orchestrator device 710),the compression metadata, and/or any other information that would beapparent to one of skill in the art in possession of the presentdisclosure as allowing for the functionality described below. In anembodiment, in response to receiving the data write compressioninstruction, the storage system 720 a may decompress the compressed datausing the compression metadata in order to provide uncompressed data,and then recompress the uncompressed data to provide compressed data,generate the compression metadata that includes the details of thecompression of that data as discussed above, and store the compresseddata and its compression metadata in one or more storage devicesincluded in the storage system 720 a. For example, the selection of boththe orchestrator device 710 and the storage system 720 a to perform datacompression operations on the data may provide for relatively“lightweight” or “simple” compression operation on the data by theorchestrator device 710 prior to transmission to the storage system 720a, followed by relatively “heavy” or “complex” compression operation bythe storage system 720 a (subsequent to decompressing the “lightweight”or “simple” compressed data received from the orchestrator device 710)prior to storing the “heavy” or “complex” compressed data in the storagesystem 720 a.

In yet another example, the selection of both the orchestrator device710 and the storage system 720 a to perform data compression operationson the data may result in the data be divided into data subsets (e.g.,equal size data subsets, unequal size data subsets, etc.), and havingthe orchestrator device 710 compress one or more of those data subsetsand transmit them along with the uncompressed data subset(s) to thestorage system 720 a, and then having the storage system 720 a compressthe uncompressed data subset(s) before storing all the compressed datasubsets in its storage device(s). In yet another example, the selectionof both the orchestrator device 710 and the storage system 720 a toperform data compression operations on the data may result in “layered”compression operations in which the orchestrator device 710 performs afirst layer of compression on the data to provide first compressed data,and the storage system 720 a performs a second layer of compression onthe first compressed data to provide second compressed data. However,while several different combined storage system/orchestrator devicecompression operations have been described, one of skill in the art inpossession of the present disclosure will recognize how the orchestratordevice and a storage system may both perform compression operations oncommon data in a variety of manners that will fall within the scope ofthe present disclosure as well.

Continuing with the specific example in which the emulated storagedevice 722 a is an emulated NVMe storage device 722 a, at block 808 andin response to the storage of the data in any of the different mannersdiscussed above, the storage controller 722 b may provide a completionmessage in an NVMe storage device completion queue of the emulated NVMestorage device 722 a, and the emulated NVMe storage device 722 a maythen generate an interrupt (e.g., a Message-Signaled Interrupt (MSI-X))to the host operating system 708 via its storage driver(s) 708 a. Inresponse, the host operating system 708 may determine that the datawrite instruction provided at block 804 has been executed.

While the orchestrator device 710 has been described above asunilaterally selecting (based on the data write compression policy andother information available to it) at least one of the storage systemand/or the orchestrator device to perform the data compressionoperations, in some embodiments the storage system may provide feedbackor otherwise participate in the compression-selection process in orderto influence the selection by the orchestrator device of the storagesystem and/or the orchestrator device to perform the data compressionoperations. For example, in some embodiments, the storage systems may beconfigured to broadcast compression availability messages to theorchestrator device 710 to indicate whether those storage systems areavailable to perform compression operations, with the orchestratordevice selecting the storage system or the orchestrator device toperform the data compression operations based on the data writecompression policy and the compression availability message(s).

In another example, in response to receiving a data write compressioninstruction that selects the storage system to perform compressionoperations, that storage system may reply to the orchestrator device 710to indicate that the system is not available to perform compressionoperations, with the orchestrator device then selecting the storagesystem or the orchestrator device to perform the data compressionoperations based on the data write compression policy and that datawrite compression instruction reply. In yet another example, the storagesystem may asynchronously request that the orchestrator device 710perform compression operations on any data is provides for storage inthat storage system, with the orchestrator device then selecting thestorage system or the orchestrator device to perform the datacompression operations based on the data write compression policy andthat asynchronous request. As such, a storage system may be configuredto negotiate the performance of compression operations with theorchestrator device, or may override a data write compressionpolicy-based decision made by the orchestrator device. As will beappreciated by one of skill in the art in possession of the presentdisclosure, the administrator of the LCS provisioning system may defineeither the orchestrator device or the storage systems as having theability to provide a “final” override and dictate where the datacompression operations will be performed (e.g., in the event bothindicate they are unavailable to perform data compression operations).

Thus, following the method 800, the data provided in the data writeinstruction from the host operating system 708 will have been compressedand stored in the storage system 720 a, with the compression operationshaving been performed based on the data write compression policy and bya resource device at a location that is most efficient considering thesize of the data being stored, the current bandwidth of the orchestratordevice to compress data, the current bandwidth of the storage system 720a to compress data, the current bandwidth of the network to transmitdata, and/or any other factors that would be apparent to one of skill inthe art in possession of the present disclosure.

Referring now to FIG. 10 , an embodiment of a method 1000 fordecompressing data for a Logically Composed System (LCS) is illustrated.As discussed below, the systems and methods of the present disclosureprovide for dynamic, policy-based utilization of decompressionfunctionality on an LCS orchestrator device and a storage system usedwith an LCS in order to perform efficient data decompression operations,and may take into account properties of the data, the state of LCSresource devices, and/or other factors in order to perform the efficientdata decompression operations discussed above while ensuring performancelevels for the LCS/LCS resource devices. For example, the LCS datadecompression system includes an orchestrator device in a resourcesystem with a host operating system and coupled to a storage system viaa network. The orchestrator device receives a read instruction from thehost operating system directed to data stored in the storage system and,in response, retrieves and uses a data read decompression policy toselect one of the storage system and the orchestrator device to performdata decompression operations on the data. The orchestrator device thenprovides a data read decompression instruction to the storage system tocause the storage system to provide the data to the orchestrator devicesuch that the orchestrator device provides the data to the hostoperation system after the one of the storage system(s) and theorchestrator device selected using the data read decompression policyperforms the data decompression operations on the data. As such, theefficiency of data decompression in a disaggregated system with avariety of decompression resources and locations is improved.

The method 1000 begins at block 1002 where an orchestrator device and astorage system(s) share decompression capabilities. With reference toFIG. 11A, in an embodiment of block 1002, the storage systems 720 a-720c and the orchestrator engine 712 in the orchestrator device 710 mayperform decompression capability exchange operations 1100 that mayinclude the orchestrator engine 712 transmitting its decompressioncapabilities via the communication system 716 and through the network718 to each of the storage systems 720 a-720 c, and each of the storagesystems 720 a-720 c transmitting their respective decompressioncapabilities through the network 718 and to the orchestrator engine 712via its communication system 716. As illustrated in FIG. 11A, inresponse to receiving the decompression capabilities from the storagesystems 720 a-720 c, the orchestrator engine 712 may performdecompression capability storage operations 1102 that include storagethose decompression capabilities in the orchestrator database 714. Aswill be appreciated by one of skill in the art in possession of thepresent disclosure, the compression capability exchange operations900/compression capability storage operations 902 discussed above asbeing performed during the method 800 and the decompression capabilityexchange operations 1100/decompression capability storage operations1102 performed during the method 1000 may be performed at the same timewhile remaining within the scope of the present disclosure.

In an embodiment, the decompression capabilities transmitted during thedecompression capability exchange operations 1100 may include anidentification of whether decompression functionality is available, atype of decompression capability that is available (e.g., adecompression algorithm that will be used in decompression operations),any of the data write decompression polic(ies) discussed below, aprotocol format for the compression metadata discussed below, and/or anyother decompression capability information that one of skill in the artin possession of the present disclosure would recognize as allowing forthe functionality discussed below. In some embodiments of block 1002,the decompression capability exchange operations 1100 may include, or befollowed by, decompression negotiation operations between the storagesystems 720 a-720 c and the orchestrator engine 712 in the orchestratordevice 710 in order to, for example, negotiate the use of compatibledecompression functionality by the orchestrator engine 712 and any ofthe storage systems 720 a-720 c. However, while the exchange ofdecompression capability information and the negotiation ofdecompression functionality has been described, one of skill in the artin possession of the present disclosure will recognize that otherinformation may be exchanged and/or other functionality negotiated inorder to provide the functionality discussed below while remainingwithin the scope of the present disclosure as well.

The method 1000 then proceeds to block 1004 where the orchestratordevice receives a data read instruction identifying data. With referenceto FIG. 11B, in an embodiment of block 1004, the orchestrator engine 712in the orchestrator device 710 may perform data read instructionreceiving operations 1104 that include receiving a data read instructionfrom the host operating system 708. For example, the host operatingsystem 708 provided for the LCS discussed above may receive aninstruction from a user (e.g., via a container, application, and/orvirtual machine provided by the host operating system 708 as discussedabove) to retrieve data and, in response, the host operating system 708may generate and transmit a data read instruction that identifies thatdata to the orchestrator engine 712 in the orchestrator device 710.

To provide a specific example in which the emulated storage device 722 ais an emulated NVMe storage device 722 a, at block 1004 a host NVMeinitiator provided by the host operating system 708 may provide the dataread instruction in an NVMe storage device submission queue of theemulated NVMe storage device 722 a, and then may ring a doorbell for theemulated NVMe storage device 722 a. In response, the emulated NVMestorage device 722 a/storage controller 722 b will read the NVMe storagedevice submission queue to retrieve the data read instruction. However,while a specific example is provided, one of skill in the art inpossession of the present disclosure will appreciate that theorchestrator engine 712 in the orchestrator device 710 may receive thedata read instruction in a variety of manners that will fall within thescope of the present disclosure as well.

The method 1000 then proceeds to block 1006 where the orchestratordevice uses a data read decompression policy to select the storagesystem or the orchestrator device to perform data decompressionoperations on the data. With reference to FIG. 11C, in an embodiment ofblock 1006, the orchestrator engine 712 in the orchestrator device 710may perform data read decompression policy retrieval operations 1106that include accessing a data read decompression policy that is storedin the orchestrator database 714. As will be appreciated by one of skillin the art in possession of the present disclosure, the data readdecompression policies described herein may be provided in orchestratordevices in resource systems (e.g., in the orchestrator device 710 in theBMS system 702 in FIG. 11C) by an administrator of the LCS provisioningsystem discussed above, and may define how data decompression operationsshould be performed for any LCS provided using that orchestrator device.As such, the data read decompression policy retrieved at block 1006 mayhave been generated and stored in the orchestrator database 714 prior tothe method 1000, and many include any of a variety of policy detailsthat provide for the data decompression functionality described below.

As will be appreciated by one of skill in the art in possession of thepresent disclosure, the data read decompression policy may include anyof a variety of policy details that define when, where, and how datawill be decompressed as part of a data read operation. For example, arelatively simple data read decompression policy may define a data sizeover which data will be transmitted to the orchestrator device withoutperforming data decompression operations on that data, and under whichdata decompression operations will be performed on that data prior totransmitting that data to the orchestrator device. As such, the dataread decompression policy may consider data transfer bandwidth savings(e.g., data transfer bandwidth savings realized via the transmission ofcompressed data vs. decompressed data) when determining how, when, andwhere to perform data decompression operations.

In another example, another relatively simple data read decompressionpolicy may define an orchestrator device processing bandwidth over whichdata will be transmitted to the orchestrator device without performingdata decompression operations on that data, and under which datadecompression operations will be performed on that data prior totransmitting that data to the orchestrator device. In another example,another relatively simple data read decompression policy may define astorage system processing bandwidth under which data will be transmittedto the orchestrator device without performing data decompressionoperations on that data, and over which data decompression operationswill be performed on that data prior to transmitting that data to theorchestrator device. As such, the data read decompression policy mayconsider CPU utilization (e.g., current CPU utilization in either orboth of the orchestrator device and the storage system) when determininghow, when, and where to perform data decompression operations.

In another example, another relatively simple data read decompressionpolicy may define network bandwidth under which data will be transmittedto the orchestrator device without performing data decompressionoperations on that data, and over which data decompression operationswill be performed on that data prior to transmitting that data to theorchestrator device. For example, the orchestrator device may beconfigured to identify a network bandwidth based on an amount of datatraffic that is being transmitted via its communication system 716(e.g., via a NIC port that is coupled to the network 718). As such, thedata read decompression policy may consider data transfer bandwidth(e.g., data transfer bandwidth currently available in the network) whendetermining how, when, and where to perform data decompressionoperations.

Furthermore, one of skill in the art in possession of the presentdisclosure will appreciate how the relatively simple data readdecompression policies discussed above may be combined to generaterelatively more complex data read decompression policies that considerdata size, orchestrator processing bandwidth, storage system processingbandwidth, network bandwidth, as well as any other factors that would beapparent to one of skill in the art in possession of the presentdisclosure. For example, at block 1106 the orchestrator engine 712 inthe orchestrator device 710 may select the storage system 720 a or theorchestrator device 710 to perform data decompression based on a datablock/shard size, processing statistics generated by the storage system720 a and/or orchestrator device 710, network statistics, informationindicative of a network bottleneck, etc. However, while a few specificdata read decompression policies have been described, one of skill inthe art in possession of the present disclosure will appreciate how dataread decompression policies of varying complexity may define when,where, and how decompression should be performed when retrievingcompressed data from a storage system and providing it to a hostoperating system while remaining within the scope of the presentdisclosure as well.

Similarly as described above for the compression operations in themethod 800, one of skill in the art in possession of the presentdisclosure will recognize that the orchestrator engine 712 in theorchestrator device 710 may have access to any of a variety ofinformation about the operation of the LCS (and the resource devicesused to provide that LCS) in order to utilize the data readdecompression policy to select a storage system or the orchestratordevice to perform data compression operations on the compressed data.For example, in order to determine the orchestrator device processingbandwidth discussed above, the orchestrator engine 712 may have accessto orchestrator processing system telemetry data and/or other operatinginformation. Similarly, in order to determine the storage systemprocessing bandwidth discussed above, the orchestrator engine 712 mayhave access to storage system processing system telemetry data and/orother operating information via the network 718. Similarly as well, inorder to determine the network bandwidth discussed above, theorchestrator engine 712 may have access to network operating informationvia its communication system 716.

As such, at block 806, the orchestrator engine 712 in the orchestratordevice 710 may use the data read decompression policy and any of theinformation discussed above in order to select one of the storagesystems 720 a-720 c or the orchestrator device 710 to perform datadecompression operations on the compressed data. In some of the specificexamples provided below, the orchestrator engine 712 in the orchestratordevice 710 selects the storage system 720 a that stores the compresseddata for performing decompression operations, but one of skill in theart in possession of the present disclosure will appreciate how theother storage systems 720 b-720 c may store the compressed data and/ormay be selected to perform the decompression operations while remainingwithin the scope of the present disclosure as well. For example, someembodiments of block 1006 may include the orchestrator engine 712 in theorchestrator device 710 using the data read decompression policy and anyof the information discussed above in order to select the orchestratordevice 710 to perform data decompression operations on the compresseddata. In another example, some embodiments of block 806 may include theorchestrator engine 712 in the orchestrator device 710 using the dataread decompression policy and any of the information discussed above inorder to select the storage system 720 a to perform data decompressionoperations on the compressed data.

In some embodiments, the data read decompression policy may define adata size threshold over which more information may be retrieved andused in order to select the storage system 720 a and/or the orchestratordevice 710 to perform the data decompression operations, and under whichthat information will not be retrieved or used in order to select thestorage system 720 a and/or the orchestrator device 710 to perform thedata decompression operations. To provide a specific example, if thehost operating system 708 provides a data read instruction for data witha size of 4 KB, the latency associated with requesting the compressionmetadata and/or other information discussed below may not justify doingso, while if the host operating system 708 requests data with a largersize, the additional latency associated with requesting the compressionmetadata and/or other information discussed below may not substantiallyincrease the latency associated with the retrieval of that data and thusmay be justified. However, one of skill in the art in possession of thepresent disclosure will appreciate how the 4 KB size threshold providedin the specific example above may be reduced in the future.

For example, with reference to FIGS. 11D and 11E and in an embodiment ofblock 1008, the data identified in the data read instruction may includea size above the data size threshold defined in the data readdecompression policy and, in response, the orchestrator engine 712 inthe orchestrator device 710 may perform compression metadata retrievaloperations 1108 that include transmitting a compression metadata requestfor compression metadata associated with the data that was requested inthe data read instruction via its communication system 716 and throughthe network 718 to the storage system 720 a. In response, storage system720 a may perform compression metadata provisioning operations 1110 thatincludes transmitting the compression metadata associated with the datathat was requested in the data read instruction through the network 718and to the orchestrator engine 712 via its communication system 716.

As discussed above, the compression metadata may include any detailsabout the compression of data that would be required by another deviceor system that did not perform that compression in order to decompressthat data, and allows the decompression operations discussed below to beperformed anywhere in the disaggregated system/LCS regardless of wherethe compression operations were performed. Furthermore, the compressionmetadata retrieved as discussed above may identify a compressionalgorithm that was used to compress the data, a compression ratio of thedecompressed data to the compressed data, a size of the decompresseddata, a size of the compressed data, a checksum for the compressed data,and/or any other compression metadata that one of skill in the art inpossession of the present disclosure would recognize as providing forthe decompression functionality described below. Thus, at block 1008,the orchestrator engine 712 in the orchestrator device 710 may utilizethe compression metadata that stores compression details about thecompressed data, along with the data read decompression policy, in orderto select the storage system 720 a and/or the orchestrator device 710 toperform the decompression operations on that compressed data, and maygenerate a data read decompression instruction that identifies thatselection.

In embodiments in which the orchestrator engine 712 in the orchestratordevice 710 selects the orchestrator device 710 to perform datadecompression operations on the compressed data, the orchestrator engine712 may operate to generate a data read decompression instruction thatidentifies the compressed data stored in the storage system 720 a andinstructs the storage system to transmit that compressed data to theorchestrator device 710. In embodiments in which the orchestrator engine712 in the orchestrator device 710 selects the storage system 720 a toperform data decompression operations on the compressed data, theorchestrator engine 712 may operate to generate a data readdecompression instruction that identifies the compressed data stored inthe storage system 720 a and instructs the storage system to decompressthat compressed data before transmitting the decompressed data to theorchestrator device 710.

The method 1000 then proceeds to block 1008 where the orchestratordevice provides a data read decompression instruction to the storagesystem to cause the storage system to provide the data to theorchestrator device such that the orchestrator device provides the datato the host operating system after the storage system or theorchestrator device selected using the data read decompression policyperforms data decompression operations on the data. With reference toFIG. 11F, in an embodiment of block 1008, the orchestrator engine 712 inthe orchestrator device 710 may perform data read decompressioninstruction transmission operations 1112 that include transmitting thedata read decompression instruction via its communication system 716 andthrough the network 718 to the storage system 720 a.

Continuing with the example above in which the orchestrator device 710was selected to perform data decompression operations, the data readdecompression instruction may identify the compressed data and/or anyother information that would be apparent to one of skill in the art inpossession of the present disclosure. With reference to FIG. 11G, in anembodiment of block 1008 and in response to receiving the data readdecompression instruction, the storage system 720 a may perform dataprovisioning operations that include providing the compressed datathrough the network 718 to the storage system 720 a via itscommunication system 716, with the orchestrator engine 712 decompressingthat compressed data (e.g., using the compression service 722 ddiscussed above with reference to FIG. 7B) to provide decompressed data.With reference to FIG. 11H, the orchestrator engine 712 in theorchestrator device 710 may then perform data provisioning operation toprovide the decompressed data to the host operating system 708, thuscompleting the data read instruction.

Continuing with the example above in which the storage system 720 a wasselected to perform data decompression operations, the data readdecompression instruction may identify the compressed data, instruct thedecompression of that compressed data, and/or provide any otherinformation that would be apparent to one of skill in the art inpossession of the present disclosure. With reference back to FIG. 11G,in an embodiment of block 1008 and in response to receiving the dataread decompression instruction, the storage system 720 a may performdata provisioning operations that include retrieving the compresseddata, decompressing that compressed data to provide uncompressed data,and providing the uncompressed data through the network 718 to theorchestrator engine 712 via its communication system 716. With referenceto FIG. 11H, the orchestrator engine 712 in the orchestrator device 710may then perform the data provisioning operations 1116 to provide thedecompressed data to the host operating system 708, thus completing thedata read instruction. As will be appreciated by one of skill in the artin possession of the present disclosure, in some embodiments the dataprovisioning operation 1116 may include the orchestrator engine 712retrieving a portion of the uncompressed data and providing only thatportion of the uncompressed data to the host operating system 708. Forexample, the data read instruction may have identified that portion ofthe data that is stored in a larger compressed block of data, and thusthe decompression of that portion of the data may require decompressionof the larger compressed block of that data, with only that portion ofthe data being returned to the host operating system 708 followingdecompression.

Continuing with the specific example in which the emulated storagedevice 722 a is an emulated NVMe storage device 722 a, at block 1008 thestorage controller 722 b may provide a completion message in an NVMestorage device completion queue of the emulated NVMe storage device 722a, and the emulated NVMe storage device 722 a may then generate aninterrupt (e.g., a Message-Signaled Interrupt (MSI-X)) to the hostoperating system 708 via its storage driver(s) 708 a. In response, thehost operating system 708 may determine that the data read instructionprovided at block 804 has been executed, and may retrieve theuncompressed data from the emulated NVMe storage device 722 a (e.g.,from physical system memory that provides the storage for the emulatedNVMe storage device 722 a).

While the orchestrator device 710 has been described above asunilaterally selecting (based on the data read decompression policy andother information available to it) the storage system or theorchestrator device to perform the data decompression operations, insome embodiments the storage system may provide feedback in order toinfluence the selection by the orchestrator device of the storage systemand/or the orchestrator device to perform the data decompressionoperations. For example, in some embodiments, the storage systems may beconfigured to broadcast decompression availability messages to theorchestrator device 710 to indicate whether those storage systems areavailable to perform decompression operations, with the orchestratordevice selecting the storage system and/or the orchestrator device toperform the data decompression operations based on the data readdecompression policy and the decompression availability me s s age(s).

In another example, in response to receiving a data read decompressioninstruction that selects the storage system to perform decompressionoperations, that storage system may reply to the orchestrator device 710to indicate that storage system is not available to performdecompression operations, with the orchestrator device then selectingthe storage system and/or the orchestrator device to perform the datadecompression operations based on the data read decompression policy andthat data read decompression instruction reply. In yet another example,the storage system may asynchronously request that the orchestratordevice 710 perform decompression operations, with the orchestratordevice then selecting the storage system and/or the orchestrator deviceto perform the data decompression operations based on the data readdecompression policy and that asynchronous request. As such, a storagesystem may be configured to negotiate the performance of decompressionoperations with the orchestrator device, or may override a data readdecompression policy-based decision made by the orchestrator device.Similarly as discussed above, the administrator of the LCS provisioningsystem may define either the orchestrator device or the storage systemsas having the ability to provide a “final” override and dictate wherethe data decompression operations will be performed (e.g., in the eventboth indicate they are unavailable to perform data decompressionoperations).

Thus, systems and methods have been described that provide for dynamic,policy-based utilization of decompression functionality on an LCSorchestrator device and a storage system used with an LCS in order toperform efficient data decompression, and may take into accountproperties of the data, the state of LCS resource devices, and/or otherfactors in order to perform the efficient data decompression discussedabove while ensuring performance levels for the LCS/LCS resourcedevices. For example, the LCS data decompression system of the presentdisclosure may include an orchestrator device in a resource system witha host operating system and coupled to a storage system via a network.The orchestrator device receives a read instruction from the hostoperating system identifying data stored in the storage system and, inresponse, retrieves and uses a data read decompression policy to selectone of the storage system and the orchestrator device to perform datadecompression operations on the data. The orchestrator device thenprovides a data read decompression instruction to the storage system tocause the storage system to provide the data to the orchestrator devicesuch that the orchestrator device provides the data to the hostoperation system after the one of the storage system and the LCSorchestrator device selected using the data read decompression policyperforms the data decompression operations on the data. As such, theefficiency of data decompression in a disaggregated system with avariety of decompression resources and locations is improved.

Although illustrative embodiments have been shown and described, a widerange of modification, change and substitution is contemplated in theforegoing disclosure and in some instances, some features of theembodiments may be employed without a corresponding use of otherfeatures. Accordingly, it is appropriate that the appended claims beconstrued broadly and in a manner consistent with the scope of theembodiments disclosed herein.

What is claimed is:
 1. An Logically Composed System (LCS) datacompression/decompression system, comprising: a resource systemproviding a host operating system for a Logically Composed System (LCS);a storage system that is used by host operating system for the LCS andthat is configured to perform data decompression operations; and an LCSorchestrator device that is included in the resource system and that isconfigured to perform the data decompression operations, wherein the LCSorchestrator device is coupled to the storage system via a network andconfigured to: receive, from the host operating system, a readinstruction to perform a read operation on data that is stored in thestorage system; retrieve, in response to receiving the read instruction,a data read decompression policy; select, using the data readdecompression policy, one of the storage system and the orchestratordevice to perform the data decompression operations on the data; andprovide, to the storage system via the network, a data readdecompression instruction that is configured to cause the storage systemto provide the data to the LCS orchestrator device such that the LCSorchestrator device provides the data to the host operation system afterthe one of the storage system and the LCS orchestrator device selectedusing the data read decompression policy performs the data decompressionoperations on the data.
 2. The system of claim 1, wherein the LCSorchestrator device is configured to: retrieve, from the storage systemvia the network, compression metadata for the data, wherein the LCSorchestrator device selects the one of the storage system and the LCSorchestrator device to perform the data decompression operations on thedata using both the data read decompression policy and the compressionmetadata for the data, wherein the data read decompression instructionis configured to cause the storage system to provide the data to the LCSorchestrator device such that the LCS orchestrator device provides thedata to the host operation system after the one of the storage systemand the LCS orchestrator device selected using the data readdecompression policy and the compression metadata performs the datadecompression operations on the data.
 3. The system of claim 2, whereinthe LCS orchestrator device is configured to: determine that the dataexceeds a data size threshold and, in response, retrieve the compressionmetadata.
 4. The system of claim 1, wherein the LCS orchestrator deviceis configured to: receive, from the storage system via the network,storage system operating information, wherein the LCS orchestratordevice selects the at least one of the storage system and the LCSorchestrator device to perform the data decompression operations on thedata using both the data read decompression policy and the storagesystem operating information, wherein the data read decompressioninstruction is configured to cause the storage system to provide thedata to the LCS orchestrator device such that the LCS orchestratordevice provides the data to the host operation system after the one ofthe storage system and the LCS orchestrator device selected using thedata read decompression policy and the storage system operatinginformation performs the data decompression operations on the data. 5.The system of claim 1, wherein the storage system and the LCSorchestrator device are each configured to perform data compressionoperations, and wherein the LCS orchestrator device is configured to:receive, from the host operating system prior to receiving the readinstruction, a write instruction to perform a write operation in thestorage system using the data that is included in the write instruction;retrieve, in response to receiving the write instruction, a data writecompression policy; select, using the data write compression policy, atleast one of the storage system and the LCS orchestrator device toperform the data compression operations on the data; and provide, to thestorage system via the network, a data write compression instructionthat provides the data for storage in the storage system after the atleast one of the storage system and the LCS orchestrator device selectedusing the data write compression policy performs the data compressionoperations on the data.
 6. The system of claim 5, wherein the LCSorchestrator device selects the orchestrator device to perform the datacompression operations on the data, and wherein the LCS orchestratordevice is configured to: generate compression metadata for the data; andprovide, to the storage system via the network, the compression metadatafor the data in the data write compression instruction.
 7. AnInformation Handling System (IHS), comprising: a processing system; anda memory system that is coupled to the processing system and thatincludes instructions that, when executed by the processing system,cause the processing system to provide a Logically Composed System (LCS)orchestrator engine that is configured to: receive, from a hostoperating system, a read instruction to perform a read operation on datathat is stored in a storage system; retrieve, in response to receivingthe read instruction, a data read decompression policy; select, usingthe data read decompression policy, one of the storage system and theLCS orchestrator engine to perform data decompression operations on thedata; and provide, to the storage system via a network, a data readdecompression instruction that is configured to cause the storage systemto provide the data to the LCS orchestrator engine such that the LCSorchestrator engine provides the data to the host operation system afterthe one of the storage system and the LCS orchestrator device selectedusing the data read decompression policy performs the data decompressionoperations on the data.
 8. The IHS of claim 7, wherein the LCSorchestrator engine is configured to: retrieve, from the storage systemvia the network, compression metadata for the data, wherein the LCSorchestrator engine selects the one of the storage system and the LCSorchestrator engine to perform the data decompression operations on thedata using both the data read decompression policy and the compressionmetadata for the data, wherein the data read decompression instructionis configured to cause the storage system to provide the data to the LCSorchestrator engine such that the LCS orchestrator engine provides thedata to the host operation system after the one of the storage systemand the LCS orchestrator engine selected using the data readdecompression policy and the compression metadata performs the datadecompression operations on the data.
 9. The IHS of claim 8, wherein theLCS orchestrator engine is configured to: determine that the dataexceeds a data size threshold and, in response, retrieve the compressionmetadata.
 10. The IHS of claim 7, wherein the LCS orchestrator engine isconfigured to: receive, from the storage system via the network, storagesystem operating information, wherein the LCS orchestrator engineselects the one of the storage system and the LCS orchestrator engine toperform the data decompression operations on the data using both thedata read decompression policy and the storage system operatinginformation, wherein the data read decompression instruction isconfigured to cause the storage system to provide the data to the LCSorchestrator engine such that the LCS orchestrator engine provides thedata to the host operation system after the one of the storage systemand the LCS orchestrator engine selected using the data readdecompression policy and the storage system operating informationperforms the data decompression operations on the data.
 11. The IHS ofclaim 7, wherein the LCS orchestrator engine is configured to: receive,from the host operating system prior to receiving the read instruction,a write instruction to perform a write operation in the storage systemusing the data that is included in the write instruction; retrieve, inresponse to receiving the write instruction, a data write compressionpolicy; select, using the data write compression policy, at least one ofthe storage system and the LCS orchestrator engine to perform the datacompression operations on the data; and provide, to the storage systemvia the network, a data write compression instruction that provides thedata for storage in the storage system after the at least one of thestorage system and the LCS orchestrator engine performs the datacompression operations on the data as selected using the data writecompression policy.
 12. The IHS of claim 7, wherein the LCS orchestratorengine selects the LCS orchestrator engine to perform the datacompression operations on the data, and wherein the LCS orchestratorengine is configured to: generate compression metadata for the data; andprovide, to the storage system via the network, the compression metadatafor the data in the data write compression instruction.
 13. The IHS ofclaim 12, wherein the compression metadata for the data includes atleast one of a compression algorithm that was used to compress the data,a compressed size of the data, a decompressed size of the data, and achecksum for the data.
 14. A method for decompressing data for aLogically Composed System (LCS), comprising: receiving, by an LogicallyComposed System (LCS) orchestrator device from a host operating system,a read instruction to perform a read operation on data that is stored ina storage system; retrieving, by the LCS orchestrator device in responseto receiving the read instruction, a data read decompression policy;selecting, by the LCS orchestrator device using the data readdecompression policy, one of the storage system and the LCS orchestratordevice to perform data decompression operations on the data; andproviding, by the LCS orchestrator device to the storage system via anetwork, a data read decompression instruction that is configured tocause the storage system to provide the data to the LCS orchestratordevice such that the LCS orchestrator device provides the data to thehost operation system after the one of the storage system and the LCSorchestrator device selected using the data read decompression policyperforms the data decompression operations on the data.
 15. The methodof claim 14, further comprising: retrieving, by the LCS orchestratordevice from the storage system via the network, compression metadata forthe data, wherein the LCS orchestrator device selects the one of thestorage system and the LCS orchestrator device to perform the datadecompression operations on the data using both the data readdecompression policy and the compression metadata for the data, whereinthe data read decompression instruction is configured to cause thestorage system to provide the data to the LCS orchestrator device suchthat the LCS orchestrator device provides the data to the host operationsystem after the one of the storage system and the LCS orchestratordevice selected using the data read decompression policy and thecompression metadata performs the data decompression operations on thedata.
 16. The method of claim 15, further comprising: determining, bythe LCS orchestrator device, that the data exceeds a data size thresholdand, in response, retrieve the compression metadata.
 17. The method ofclaim 14, further comprising: receiving, by the LCS orchestrator devicefrom the storage system via the network, storage system operatinginformation, wherein the LCS orchestrator device selects the one of thestorage system and the LCS orchestrator device to perform the datadecompression operations on the data using both the data readdecompression policy and the storage system operating information,wherein the data read decompression instruction is configured to causethe storage system to provide the data to the LCS orchestrator devicesuch that the LCS orchestrator device provides the data to the hostoperation system after the one of the storage system and the LCSorchestrator device selected using the data read decompression policyand the storage system operating information performs the datadecompression operations on the data.
 18. The method of claim 14,further comprising: receiving, by the LCS orchestrator device from thehost operating system prior to receiving the read instruction, a writeinstruction to perform a write operation in the storage system using thedata that is included in the write instruction; retrieving, by the LCSorchestrator device in response to receiving the write instruction, adata write compression policy; selecting, by the LCS orchestrator deviceusing the data write compression policy, at least one of the storagesystem and the LCS orchestrator device to perform the data compressionoperations on the data; and providing, by the LCS orchestrator device tothe storage system via the network, a data write compression instructionthat provides the data for storage in the storage system after the atleast one of the storage system and the LCS orchestrator device performsthe data compression operations on the data as selected using the datawrite compression policy.
 19. The method of claim 14, wherein the LCSorchestrator device selects the LCS orchestrator device to perform thedata compression operations on the data, and wherein the method furthercomprises: generating, by the LCS orchestrator device, compressionmetadata for the data; and providing, by the LCS orchestrator device tothe storage system via the network, the compression metadata for thedata in the data write compression instruction.
 20. The method of claim19, wherein the compression metadata for the data includes at least oneof a compression algorithm that was used to compress the data, acompressed size of the data, a decompressed size of the data, and achecksum for the data.